Skip to content

[AMD] dsv4-fp4-mi355x-atom: enable DPA at high concurrency, update image to atom0.1.4#1717

Merged
seungrokj merged 36 commits into
mainfrom
amd/dsv4_atom_0612
Jun 18, 2026
Merged

[AMD] dsv4-fp4-mi355x-atom: enable DPA at high concurrency, update image to atom0.1.4#1717
seungrokj merged 36 commits into
mainfrom
amd/dsv4_atom_0612

Conversation

@seungrokj

@seungrokj seungrokj commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Update image to rocm/atom:rocm7.2.4_ubuntu24.04_py3.12_pytorch_release_2.10.0_atom0.1.4_20260612
  • Enable on top of DPA+TP8 at high concurrency:
    • ISL=1024 / OSL=1024
    • ISL=8192 / OSL=1024
  • Update ISL=8192 search-space: TP8-only conc=4–64, DPA conc=128–1024 (previously conc=1–64 and DPA conc=64–512)
  • Add perf-changelog entry

Motivation

Based on Pareto frontier analysis from ATOM runs 27367309656 and 27030375093,

Test plan

  • Verify bash -n syntax check passes on dsv4_fp4_mi355x_atom.sh

🤖 Generated with Claude Code


Note

Medium Risk
Changes benchmark matrix size and ATOM serving flags (DPA/TBO, memory, caching) for a large model on MI355X, which can affect sweep cost, stability, and comparability to prior runs—not app security, but meaningful for CI/perf regression signal.

Overview
Updates DeepSeek-V4 FP4 / MI355X / ATOM benchmark coverage and how the runner starts the server.

dsv4-fp4-mi355x-atom in amd-master.yaml switches the container to rocm/atom-dev:nightly_202606161823 and drops the old day-0 “CONC=1 only” comment block. For 1K/1K, DPA sweeps now run through conc 2048 (was capped at 1024). For 8K/1K, the search space is reworked: explicit TP4 and TP8 conc-list low-concurrency points replace the prior TP8-only conc 1–64 + DPA 64–512 layout, and DPA runs from conc 128 through 2048.

dsv4_fp4_mi355x_atom.sh turns on --enable-tbo with GPU_MAX_HW_QUEUES=5 when DPA is enabled at high concurrency (1K/1K ≥1024, 8K/1K ≥256). Server launch adds CUDA graph capture sizes, --gpu-memory-utilization 0.9, --no-enable_prefix_caching, and use_index_cache / index_topk_freq HF overrides. EVAL_ONLY now sets EVAL_MAX_MODEL_LEN via compute_eval_context_length.

perf-changelog.yaml documents the config change (note: changelog text references a different atom0.1.4 image tag than the YAML pin in this diff).

Reviewed by Cursor Bugbot for commit bcf0d1f. Bugbot is set up for automated code reviews on this repo. Configure here.

seungrokj and others added 2 commits June 12, 2026 21:38
…e image to atom0.1.4

- Enable --enable-tbo for ISL=1024/OSL=1024 at CONC>=1024 and ISL=8192/OSL=1024 at CONC>=256
- Update image to atom0.1.4_20260612
- Update ISL=8192 search-space to start at conc=4 and use DPA from conc=128

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers.

If additional help is needed, PR authors can reach out to core maintainers over Slack.

2 similar comments
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers.

If additional help is needed, PR authors can reach out to core maintainers over Slack.

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers.

If additional help is needed, PR authors can reach out to core maintainers over Slack.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

…onc range

- Pass --max-model-len to server using SERVE_MAX_MODEL_LEN
- Add EVAL_ONLY path: compute eval context length via compute_eval_context_length
- Extend conc-end to 8192 (isl=1024) and 4096 (isl=8192) in amd-master.yaml

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

…sable max-model-len

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Comment thread .github/configs/amd-master.yaml Outdated
Comment thread benchmarks/single_node/fixed_seq_len/dsv4_fp4_mi355x_atom.sh Outdated
…m-seqs

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Comment thread benchmarks/single_node/fixed_seq_len/dsv4_fp4_mi355x_atom.sh
@functionstackx

Copy link
Copy Markdown
Collaborator

can u rebase it so the sweep triggers?

…e, enable max-model-len

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Comment thread .github/configs/amd-master.yaml Outdated
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@seungrokj seungrokj changed the title [AMD] dsv4-fp4-mi355x-atom: enable DPA TBO at high concurrency, update image to atom0.1.4 [AMD] dsv4-fp4-mi355x-atom: enable DPA at high concurrency, update image to atom0.1.4 Jun 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

…nch override

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

…/TP8/DPA

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

@seungrokj

Copy link
Copy Markdown
Collaborator Author

@functionstackx @cquil11 can you please merge this ?

@chunfangamd chunfangamd left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@seungrokj

Copy link
Copy Markdown
Collaborator Author

/reuse-sweep-run

@seungrokj

Copy link
Copy Markdown
Collaborator Author

/merge-prs

@Oseltamivir Oseltamivir left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

seungrokj and others added 2 commits June 18, 2026 09:38
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 471aff2. Configure here.

Comment thread perf-changelog.yaml
@seungrokj seungrokj merged commit 60bf726 into main Jun 18, 2026
26 checks passed
@seungrokj seungrokj deleted the amd/dsv4_atom_0612 branch June 18, 2026 00:56
@Oseltamivir Oseltamivir restored the amd/dsv4_atom_0612 branch June 18, 2026 01:19
Oseltamivir added a commit that referenced this pull request Jun 18, 2026
* [AMD] dsv4-fp4-mi355x-atom: enable DPA TBO at high concurrency, update image to atom0.1.4

- Enable --enable-tbo for ISL=1024/OSL=1024 at CONC>=1024 and ISL=8192/OSL=1024 at CONC>=256
- Update image to atom0.1.4_20260612
- Update ISL=8192 search-space to start at conc=4 and use DPA from conc=128

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] perf-changelog: dsv4-fp4-mi355x-atom DPA TBO + image atom0.1.4

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] perf-changelog: add PR link #1717

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4_fp4_mi355x_atom.sh: disable prefix caching

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4-fp4-mi355x-atom: add max-model-len, eval context, extend conc range

- Pass --max-model-len to server using SERVE_MAX_MODEL_LEN
- Add EVAL_ONLY path: compute eval context length via compute_eval_context_length
- Extend conc-end to 8192 (isl=1024) and 4096 (isl=8192) in amd-master.yaml

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4-fp4-mi355x-atom: narrow eval to single conc=1024 point, disable max-model-len

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4_fp4_mi355x_atom.sh: add cudagraph-capture-sizes and max-num-seqs

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4-fp4-mi355x-atom: bump to nightly image, expand search space, enable max-model-len

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] set GPU_MAX_HW_QUEUES=5 in dsv4_fp4_mi355x_atom.sh

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4-fp4-mi355x-atom: disable TBO, add TP4 rows for isl=8192, cap conc ranges

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4_fp4_mi355x_atom.sh: quote SERVER_LOG variable

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4_fp4_mi355x_atom.sh: comment out dense cudagraph sizes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4_fp4_mi355x_atom.sh: fix --hf-overrides JSON escaping

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4_fp4_mi355x_atom.sh: comment out dense cudagraph sizes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4-fp4-mi355x-atom: expand search space, restore isl=1024 rows

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] perf-changelog: update dsv4-fp4-mi355x-atom image and search-space description

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] dsv4_fp4_mi355x_atom.sh: restore sparse cudagraph capture sizes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] perf-changelog: revert dsv4-fp4-mi355x-atom image/search-space, remove stale entries

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* [AMD] perf-changelog: add dsv4-fp4-mi355x-sglang entry for PR #1762

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* update dsv4-fp4-mi355x-atom: bump image, enable TBO conditionally, fix mem frac

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* expand dsv4-fp4-mi355x-atom search space: restore ISL1024 scenarios, add TP4/TP8 conc lists for ISL8192

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Update perf-changelog.yaml

* Update perf-changelog.yaml

* Update perf-changelog.yaml

* Update perf-changelog.yaml

* update perf-changelog: move dsv4-fp4-mi355x-atom entry to end

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* narrow dsv4-fp4-mi355x-atom to DPA conc=256-2048 ISL8192, fix TBO branch override

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* restore full dsv4-fp4-mi355x-atom search space: ISL1024 + ISL8192 TP4/TP8/DPA

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* chore: retrigger dsv4 atom benchmark sweep

---------

Co-authored-by: seungrokj <seungrok.jung@amd.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: seungrokj <144636725+seungrokj@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Development

Successfully merging this pull request may close these issues.

4 participants